Configuration

Once the installation is finished, open CEX PDI Builder and select the unit.

../_images/cex_id.png

CEX ID

If it is correctly connected, CEX PDI Builder will display the mode in which the connected unit is. In addition, a PDI error button pdi_errors will appear:

../_images/cex_pdi_builder.png

CEX PDI Builder

  • CEX mode: CEX unit should appear in Normal mode, as shown in the figure above, or Maintenance mode.

    It can also appear as Maintenance mode (loaded with errors) or Normal mode - Disconnected.

    Note

    Maintenance mode (loaded with errors) appears when something is wrong in the configuration. For more information, see Maintenance mode (loaded with errors) - Troubleshooting section of this manual.

  • pdi_errors PDI Errors button: The user can check if the connected unit has PDI Errors by simply clicking on it. If there are no errors, the following message appears:

    ../_images/cex_pdi_builder_pdi_errors_button_message.png

    CEX PDI Builder - PDI Errors message

The user can access now to 3 configuration options:

../_images/configuration_options.png

CEX PDI Builder Options

  • CEX: It allows the user to work with offline configurations. A previously exported CEX PDI can be opened and modified or it is possible to build a new one from the default configuration.

    Note

    When an offline configuration is opened, the user can choose between working with CEX with GPIOs or ARINC.

    It is recommended to select the same hardware version that the user’s CEX has, so that if the user wishes to load this configuration later to the CEX, there will be no compatibility problems.

    ../_images/hardware_versions.png

    Hardware versions

  • Upload PDI: A previously exported CEX PDI configuration can be imported to the linked CEX.

    Warning

    When a configuration is loaded into CEX with a version older than the software version being used, an automatic migration from the configuration version to the software version being used will be performed.

    For more information on this, consult the Migrate configuration - Troubleshooting section of this manual.

  • Open CEX: By clicking on this option, CEX PDI Builder configuration menu opens with the configuration (the PDI files) loaded in the CEX. Then, the user can modify it online.

Note

PDI files are CEX configuration files. These PDI files are stored in the setup folder, holding several .xml files which contain all the control system and parameters.

../_images/pdis_files.png

PDIs files

Finally, click on ‘CEX’ to edit a configuration offline or ‘Open CEX’ to open the configuration and start editing it online.

Note

The CEX unit must enter Maintenance mode for the user to start editing, so it is necessary to accept the confirmation panel below.

../_images/cex_pdi_builder_maintenance_mode_blue.png

Open CEX

Once in Maintenance mode, the user can access the Initial menu. The different ‘buttons’ that can be seen in this menu of the CEX PDI Builder are explained below.

../_images/initial_menu.PNG

Initial menu

  1. Save and close: After changes are done, press on the save button to apply the changes in the PDI files.

    While saving, a percentage of saving process is displayed.

    ../_images/save_close.png

    Save and close

    In order to save the configuration in the CEX unit it is necessary to RESET, therefore the CEX PDI Builder software will close. For this reason, the user must accept the following panels:

    ../_images/confirmation_panels.png

    Confirmation panel - Save

    Danger

    As CEX is reset, it is not advisable to save changes during flight tests.

    Note

    This button will only appear if a CEX unit is connected, i.e. when working offline this button will not be available.

  2. Export PDI: After modifying a configuration, press the export button to store the configuration in the local storage. Users can store this configuration in an empty folder or in the folder where the previously imported configuration is stored.

    With the latter option, the “original” configuration will be overwritten by the one with the new changes.

  3. Import PDI from repo: The user can import a configuration file from the repo and modify it. After that, if the save button is pressed, this configuration will be uploaded in the CEX.

  4. Import PDI from local storage: The user can import a configuration file from the local storage and modify it. After that, if the save button is pressed, this configuration will be loaded into the CEX.

  5. Feedback: Users can report a problem they have encountered by creating an issue in their own ‘Joint Collaboration Framework’. The ‘Download’ button downloads a zipped folder with the current CEX configuration and more information needed for Embention to resolve the issue. It is advisable to attach this folder when creating the issue.

    Note

    The user’s ‘Joint Collaboration Framework’ is simply a own Github repository for each customer.

    If the user has any questions about this Joint Collaboration Framework, please see Joint Collaboration Framework user manual or contact sales@embention.com.

    ../_images/feedback.png

    Feedback

  6. These are the different functions of CEX. They are explained in the following sections.